Thank you; it's promising.

• We need RTL support
• I see that human_size_limit and human_time_limit are not i18n
• Languages list if static at the moment: requiring manually modifying two files to add a new locale. With translatewiki adding more all the time, we'd want something automatic

FYI (but it's a different PR) I believe there might be some strings in the backend (error message?) that would also require integration to completely close this

Very good job, I'm happy to see we are already quite close to have completed this task.

I think you've forgot to i18n the footer as well.

I propose to split the integration with TranslateWiki to another PR, we would already benefit from merging this PR once concerns have been addressed (Right To Left support is very important, I don't know if it works as of today, please test and confirm/adapt). @rgaudin are you ok with it?

Regarding @rgaudin comment about the automatic detection of new languages added, I do not think it is mandatory, especially it should not break lazy loading of translations. I do not mind to have to edit one more file everytime a new language is added (I imagine TranslateWiki folks might even be able to do it themselves when they add new languages).

Would you mind to create the "secret" qqq language where TranslateWiki expects to have translation instructions in English?

TranslateWiki Integration: Formal integration with TranslateWiki is pending.

I will take care of that once PR is merged

Automated Browser Language Detection Improvement: While initial support for detecting the browser's language is implemented, further testing and refinements is needed across different browsers and user configurations.

Do you have something special in mind to be tested? Or is it just "normal" testing?

Preparation for TranslateWiki: Organizing and documenting the translation file structure to facilitate future integration with TranslateWiki.

I think the only thing left is to add the qqq magic language with translation instructions. Do you have something else in mind?

FYI (but it's a different PR) I believe there might be some strings in the backend (error message?) that would also require integration to completely close this

Definitely a second step, let's finish this first one for now.

Thank you, we are getting closer but you broke few things in your last commits (see conversations)

Please do not spend too much time fine-tuning the exact words of French and Farsi translations, since you've made them with an automated translation tool we will not merge them anyway, they will have to be translated by native speakers on TranslateWiki.

Other topics to address:

• you updated all locales but not the qqq.json, while it is probably the most important one
• why did you sometimes place HTML code inside the text to translate (e.g. app.thanksToMozilla) and other times you split the text is many substrings (e.g faq.gotErrorDesc1 and faq.gotErrorDesc2) ? I believe it would be way simpler in most situations (e.g. not when HTML code is too complex, but in every other situations) to always have HTML code inside the translation and one single string to translate, it will make the translator work way easier rather than being presented with only few words out of any context, or even a dot or a comma to not forget at the beginning of a translation
  • e.g you should have only one footer string (app is a bit vague) and its value should be Powered by <a target="_blank" href="https://kiwix.org">Kiwix</a> and <a target="_blank" href="https://webrecorder.net">Webrecorder</a>, thanks to a <a target="_blank" href="https://www.mozilla.org/moss/">Mozilla Open-Source Support</a> Award
• limits in Request.vue JS code are still not handled properly:
  • they are not translated like in the Faq.vue
  • pluralization is not handled
• "+" buttons of the FAQ are still not on the left when RTL language is used
  • please have a look, if it is too complex I do not mind to move this to an issue for later fix, it is not a big usability concern

Thank you, we are getting closer to merging this.

Still some comments in conversation plus few below.

• I just realized that the zimit logo was previously centered on the page while it is not left or right ; you must put it back to center (sorry to not have realized this before, I did not got it right)
• FYI, we will not integrate with TranslateWiki right away, I will open an issue with details on what still has to be done (but does not have to be addressed in this issue)

I'm sorry, looks like we didn't understood us well regarding the centering of the logo. I wanted to center only the logo, but not move the language button.

Expected UI in English:

Expected UI in Farsi:

Rest is OK now

This is not working as expected, logo size is altered.

Wouldn't it be simpler to move the select box out of the header, keep the header as it was and put an absolute positioning to the select box?

One more thing ... Are you constantly generating code with a code generator? This is pretty annoying to spend so much time in reviews detecting code which means just nothing, or changes which are meaningless (random spaces added everywhere, ...)